Skip to contentSkip to conversation

glibc: stable 2.37 branch updates.

mickledore [email protected] 6 participants 14 messages Oct 5, 2023 – Oct 20, 2023 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

From: Yash Shinde <[email protected]>

b4e23c75ae tunables: Terminate if end of input is reached (CVE-2023-4911) 2dfd8c77b5 i686: Regenerate ulps
94ef701365 Document CVE-2023-4806 and CVE-2023-5156 in NEWS
4473d1b87d Fix leak in getaddrinfo introduced by the fix for CVE-2023-4806 [BZ #30843] 9d5c6e27ed x86: Fix for cache computation on AMD legacy cpus.
79310b45af x86/dl-cacheinfo: remove unsused parameter from handle_amd 6529a7466c getaddrinfo: Fix use after free in getcanonname (CVE-2023-4806) b752934602 CVE-2023-4527: Stack read overflow with large TCP responses in no-aaaa mode 1a7cbe52c8 elf: Move l_init_called_next to old place of l_text_end in link map bdb594afa5 elf: Remove unused l_text_end field from struct link_map a7e34a6675 elf: Always call destructors in reverse constructor order (bug 30785) 3d24d1903d elf: Do not run constructors for proxy objects
be26b29262 io: Fix record locking contants for powerpc64 with __USE_FILE_OFFSET64 0d500bfdc0 hurd: Make exception subcode a long
f94ff95e93 x86: Fix incorrect scope of setting shared_per_thread [BZ# 30745] cc8243fb0b x86: Use 3/4*sizeof(per-thread-L3) as low bound for NT threshold. 80a8c858a5 x86: Fix slight bug in shared_per_thread cache size calculation. 1caf955269 x86: Increase non_temporal_threshold to roughly sizeof_L3 / 4

Dropped 0023-CVE-2023-4527.patch and 0024-CVE-2023-4806.patch files as they are present in glibc version update.

---
 meta/recipes-core/glibc/glibc-version.inc     |   2 +-
 .../glibc/glibc/0023-CVE-2023-4527.patch      | 219 -----------
 .../glibc/glibc/0024-CVE-2023-4806.patch      | 342 ------------------
 meta/recipes-core/glibc/glibc_2.37.bb         |   2 -
 4 files changed, 1 insertion(+), 564 deletions(-)
 delete mode 100644 meta/recipes-core/glibc/glibc/0023-CVE-2023-4527.patch
 delete mode 100644 meta/recipes-core/glibc/glibc/0024-CVE-2023-4806.patch
meta/recipes-core/glibc/glibc-version.inc +1 -1
index ff2b2ade9d..7eacfec778 100644
@@ -1,6 +1,6 @@
 SRCBRANCH ?= "release/2.37/master"
 PV = "2.37"
-SRCREV_glibc ?= "58f7431fd77c0a6dd8df08d50c51ee3e7f09825f" 
+SRCREV_glibc ?= "b4e23c75aea756b4bddc4abcf27a1c6dca8b6bd3"
 SRCREV_localedef ?= "794da69788cbf9bf57b59a852f9f11307663fa87"
 
 GLIBC_GIT_URI ?= "git://sourceware.org/git/glibc.git;protocol=https"
meta/recipes-core/glibc/glibc/0023-CVE-2023-4527.patch deleted +0 -219

219 lines not on this page · raw message

meta/recipes-core/glibc/glibc/0024-CVE-2023-4806.patch deleted +0 -342

342 lines not on this page · raw message

meta/recipes-core/glibc/glibc_2.37.bb +0 -2
index bce566acd4..3387441cad 100644
@@ -49,8 +49,6 @@ SRC_URI =  "${GLIBC_GIT_URI};branch=${SRCBRANCH};name=glibc \
            file://0020-tzselect.ksh-Use-bin-sh-default-shell-interpreter.patch \
            file://0021-fix-create-thread-failed-in-unprivileged-process-BZ-.patch \
            file://0022-Avoid-hardcoded-build-time-paths-in-the-output-binar.patch \
-           file://0023-CVE-2023-4527.patch \
-           file://0024-CVE-2023-4806.patch \
 "
 S = "${WORKDIR}/git"
 B = "${WORKDIR}/build-${TARGET_SYS}"
Signature · 1 line
2.39.0
#1 lore raw

Regression testing is done and below are the test results.

Before glibc update
Summary of test results:
PASS:4727
FAIL:240
XPASS:4
XFAIL:16
UNSUPPORTED:220

After glibc update
Summary of test results:
PASS:4729
FAIL:239
XPASS:4
XFAIL:16
UNSUPPORTED:221

These are the newly added test cases
PASS: io/tst-fcntl-lock-lfs
UNSUPPORTED: nss/mtrace-tst-nss-gai-hv2-canonname

And below are new failures
FAIL: nptl/tst-thread-affinity-pthread
FAIL: nptl/tst-thread-affinity-pthread2
FAIL: nptl/tst-thread-affinity-sched

And below are new passes
PASS: malloc/tst-mallocfork3-mcheck
PASS: nptl/tst-pthread-setuid-loop
PASS: resolv/tst-ns_name_length_uncompressed
PASS: string/test-strcasecmp

#3 lore raw
Quoted 2 lines · Sundeep KOKKONDA via lists.openembedded.org

Yocto bug https://bugzilla.yoctoproject.org/show_bug.cgi?id=15231 raised for failures cases analysis.

I assume that I should wait to take this patch until the analysis is done?

Steve

Quoted 8 lines

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188985): https://lists.openembedded.org/g/openembedded-core/message/188985
Mute This Topic: https://lists.openembedded.org/mt/101774187/3620601
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

A message that is not in the archive (sent off-list or not yet received): [email protected]

#5 lore raw
Quoted 8 lines · Steve Sakoman via lists.openembedded.org
Quoted 2 lines · Sundeep KOKKONDA via lists.openembedded.org

Yocto bug https://bugzilla.yoctoproject.org/show_bug.cgi?id=15231 raised for failures cases analysis.

I assume that I should wait to take this patch until the analysis is done?

Sorry, I mistakenly thought this was a new patch! Please disregard my comment :-)

Steve

Quoted 11 lines
Quoted 2 lines

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#189000): https://lists.openembedded.org/g/openembedded-core/message/189000
Mute This Topic: https://lists.openembedded.org/mt/101774187/3620601
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#6 lore raw
In reply to Sanjana V

Thanks for the update and reduced list of pass/fails, its really useful. How much memory does the device under test have ?

Quoted 43 lines · Sanjana V

Regression testing is done and below are the test results.

Before glibc update
Summary of test results:
PASS:4727
FAIL:240
XPASS:4
XFAIL:16
UNSUPPORTED:220

After glibc update
Summary of test results:
PASS:4729
FAIL:239
XPASS:4
XFAIL:16
UNSUPPORTED:221

These are the newly added test cases
PASS: io/tst-fcntl-lock-lfs
UNSUPPORTED: nss/mtrace-tst-nss-gai-hv2-canonname

And below are new failures
FAIL: nptl/tst-thread-affinity-pthread
FAIL: nptl/tst-thread-affinity-pthread2
FAIL: nptl/tst-thread-affinity-sched

And below are new passes
PASS: malloc/tst-mallocfork3-mcheck
PASS: nptl/tst-pthread-setuid-loop
PASS: resolv/tst-ns_name_length_uncompressed
PASS: string/test-strcasecmp

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188984): https://lists.openembedded.org/g/openembedded-core/message/188984
Mute This Topic: https://lists.openembedded.org/mt/101774187/1997914
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#7 lore raw

Hi Khem,

Thanks very much for checking the results and your comments.

Quoted 1 line
Quoted 1 line

How much memory does the device under test have?

We are using the default memory assigned in qemu x86-64. cat /proc/meminfo
MemTotal:228876 kB

Can you please let us know if we should increase the memory in the image while running oe-selftest?

#8 lore raw
Quoted 10 lines · Sanjana V

Hi Khem,

Thanks very much for checking the results and your comments.

Quoted 1 line
Quoted 1 line

How much memory does the device under test have?

We are using the default memory assigned in qemu x86-64. cat /proc/meminfo
MemTotal:228876 kB

For tests can you raise it to say 512mb and see if results are still same Secondly how many cpus are there ? Maybe have atleast 2 or more

Quoted 15 lines

Can you please let us know if we should increase the memory in the image while running oe-selftest?

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#188992):
https://lists.openembedded.org/g/openembedded-core/message/188992
Mute This Topic: https://lists.openembedded.org/mt/101774187/1997914
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#9 lore raw

Hi Khem,

We tried increasing the memory and no regression failures were found.

Here is the test results:

Regression testing is done and below are the test results. Before glibc update
Summary of test results:
PASS:4727
FAIL:240
XPASS:4
XFAIL:16
UNSUPPORTED:220

After glibc update
Summary of test results:
PASS:4733
FAIL:235
XPASS:4
XFAIL:16
UNSUPPORTED:221

These are the newly added test cases
PASS: io/tst-fcntl-lock-lfs
UNSUPPORTED: nss/mtrace-tst-nss-gai-hv2-canonname

These are the tests which were failing before and passed after increasing the memory:
PASS: nptl/tst-thread-affinity-pthread
PASS: nptl/tst-thread-affinity-pthread2
PASS: nptl/tst-thread-affinity-sched

#10 lore raw
Quoted 5 lines · Sanjana.Venkatesh via lists.openembedded.org

Hi Khem,

We tried increasing the memory and no regression failures were found.

Thanks for following up

Steve

We can cherry pick this for mickledore I think now

Here is the test results:

Quoted 39 lines

Regression testing is done and below are the test results. Before glibc update
Summary of test results:
PASS:4727
FAIL:240
XPASS:4
XFAIL:16
UNSUPPORTED:220

After glibc update
Summary of test results:
PASS:4733
FAIL:235
XPASS:4
XFAIL:16
UNSUPPORTED:221

These are the newly added test cases
PASS: io/tst-fcntl-lock-lfs
UNSUPPORTED: nss/mtrace-tst-nss-gai-hv2-canonname

These are the tests which were failing before and passed after increasing the memory:
PASS: nptl/tst-thread-affinity-pthread
PASS: nptl/tst-thread-affinity-pthread2
PASS: nptl/tst-thread-affinity-sched

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#189449):
https://lists.openembedded.org/g/openembedded-core/message/189449
Mute This Topic: https://lists.openembedded.org/mt/101774187/1997914
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#11 lore raw
Quoted 11 lines · Khem Raj
Quoted 5 lines · Sanjana.Venkatesh via lists.openembedded.org

Hi Khem,

We tried increasing the memory and no regression failures were found.

Quoted 5 lines

Thanks for following up

Steve

We can cherry pick this for mickledore I think now

Done!

Steve

Quoted 40 lines
Quoted 20 lines

Here is the test results:

Regression testing is done and below are the test results. Before glibc update
Summary of test results:
PASS:4727
FAIL:240
XPASS:4
XFAIL:16
UNSUPPORTED:220

After glibc update
Summary of test results:
PASS:4733
FAIL:235
XPASS:4
XFAIL:16
UNSUPPORTED:221

Quoted 11 lines

These are the newly added test cases
PASS: io/tst-fcntl-lock-lfs
UNSUPPORTED: nss/mtrace-tst-nss-gai-hv2-canonname

These are the tests which were failing before and passed after increasing the memory:
PASS: nptl/tst-thread-affinity-pthread
PASS: nptl/tst-thread-affinity-pthread2
PASS: nptl/tst-thread-affinity-sched

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#189488): https://lists.openembedded.org/g/openembedded-core/message/189488
Mute This Topic: https://lists.openembedded.org/mt/101774187/3620601
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#12 lore raw
In reply to Khem Raj

Hi Khem,

We tried increasing the memory and no regression failures were found.

Here is the test results:

Regression testing is done and below are the test results. Before glibc update
Summary of test results:
PASS:4727
FAIL:240
XPASS:4
XFAIL:16
UNSUPPORTED:220

After glibc update
Summary of test results:
PASS:4733
FAIL:235
XPASS:4
XFAIL:16
UNSUPPORTED:221

These are the newly added test cases
PASS: io/tst-fcntl-lock-lfs
UNSUPPORTED: nss/mtrace-tst-nss-gai-hv2-canonname

These are the tests which were failing before and passed after increasing the memory:
PASS: nptl/tst-thread-affinity-pthread
PASS: nptl/tst-thread-affinity-pthread2
PASS: nptl/tst-thread-affinity-sched

#13 lore raw
In reply to Khem Raj

Hi Khem,

We have checked by raising the memory and no regression failures were found.

Here is the test summary;

Regression testing is done and below are the test results. Before glibc update
Summary of test results:
PASS:4727
FAIL:240
XPASS:4
XFAIL:16
UNSUPPORTED:220

After glibc update
Summary of test results:
PASS:4733
FAIL:235
XPASS:4
XFAIL:16
UNSUPPORTED:221

These are the newly added test cases
PASS: io/tst-fcntl-lock-lfs
UNSUPPORTED: nss/mtrace-tst-nss-gai-hv2-canonname

And these are tests that were failing earlier and passed after raising the memory
PASS: nptl/tst-thread-affinity-pthread
PASS: nptl/tst-thread-affinity-pthread2
PASS: nptl/tst-thread-affinity-sched

#14 lore raw
In reply to Khem Raj

Hi Khem ,

We tried increasing the memory and no regression failures were found.

Here is the test results:

Regression testing is done and below are the test results. Before glibc update
Summary of test results:
PASS:4727
FAIL:240
XPASS:4
XFAIL:16
UNSUPPORTED:220

After glibc update
Summary of test results:
PASS:4733
FAIL:235
XPASS:4
XFAIL:16
UNSUPPORTED:221

These are the newly added test cases
PASS: io/tst-fcntl-lock-lfs
UNSUPPORTED: nss/mtrace-tst-nss-gai-hv2-canonname

These are the tests which are failing before and now it is passing
PASS: nptl/tst-thread-affinity-pthread
PASS: nptl/tst-thread-affinity-pthread2
PASS: nptl/tst-thread-affinity-sched